Performance metrics collection and promulgation from within a mobile application

ABSTRACT

A mobile communication device. The device comprises a central processing unit (CPU), a graphics processing unit (GPU), and a memory comprising a mobile application incorporating a search client that. When executed by at least one of the CPU and the GPU, the application receives an input selecting the search client, begins execution in a trusted security zone execution mode wherein instructions of the search client execute in the GPU, creates a genesis block of a block chain via the search client instructions executing in the GPU, creates an event block of the block chain via the search client instructions executing in the GPU, attaches the event block to the block chain via the search client instructions executing in the GPU, transmits the block chain to a data store, and reverts to execution in a normal execution mode.

CROSS-REFERENCE TO RELATED APPLICATIONS

None.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Mobile communication devices are widely deployed and used by people inall walks of life in the United States and other nations. Mobilecommunication devices provide both voice communication services and datacommunication services. People can hold voice conversations with othersvia their mobile communication devices. People can access the Internetand download content via browsers executing on their mobilecommunication devices. Additionally, mobile applications or computerprograms may be installed on the mobile communication device. Whenexecuted, the mobile applications may process autonomously on the mobilecommunication device. The mobile applications may also interact withapplication servers that assist the mobile applications in some way. Insome cases, the mobile application may be deployed as a client havinglimited capabilities that executes on the mobile communication devicethat interworks with a server application that executes on a servercomputer accessible via a wireless connection from the mobilecommunication device. Mobile communication devices may have an operatingsystem installed that provides an execution environment. This operatingsystem may constrain or limit what mobile applications are able to do.

SUMMARY

In an embodiment, a method of performing an Internet search from withina mobile application is disclosed. The method comprises executing amobile application in a normal execution mode on a mobile communicationdevice, where the mobile application incorporates an Internet searchclient, in response to receiving an input to the mobile applicationselecting the Internet search client, executing the mobile applicationin a trusted security zone execution mode on the mobile communicationdevice wherein the mobile application executes instructions of theInternet search client in a graphics processing unit (GPU) of the mobilecommunication device, and creating a genesis block of a block chain bythe Internet search client instructions executing in the GPU, where thegenesis block comprises information about the mobile communicationdevice and about a search prompt. The method further comprises creatingan event block of the block chain by the Internet search clientinstructions executing in the GPU, where the event block comprisesinformation about at least one processing event associated withexecuting an Internet search, attaching the event block to the blockchain by the Internet search client instructions executing in the GPU,closing the block chain by the Internet search client instructionsexecuting in the GPU, transmitting the block chain by the mobilecommunication device to a data store, and reverting by the mobileapplication to execution in the normal execution mode.

In another embodiment, a mobile communication device is disclosed. Themobile communication device comprises a central processing unit (CPU), agraphics processing unit (GPU), and a non-transitory memory comprising amobile application incorporating an Internet search client. Whenexecuted by at least one of the CPU and the GPU, the mobile applicationreceives an input selecting the Internet search client. In response tothe input, the mobile application begins execution in a trusted securityzone execution mode wherein instructions of the Internet search clientexecute in the GPU. The mobile application creates a genesis block of ablock chain via the Internet search client instructions executing in theGPU, where the genesis block comprises information about the mobilecommunication device and about a search prompt. The mobile applicationfurther creates an event block of the block chain via the Internetsearch client instructions executing in the GPU, where the event blockcomprises information about at least one processing event associatedwith executing an Internet search. The mobile application attaches theevent block to the block chain via the Internet search clientinstructions executing in the GPU, transmits the block chain to a datastore, and reverts to execution in a normal execution mode.

In yet another embodiment, a method of executing a mobile application isdisclosed. The method comprises executing a mobile application in anormal execution mode on a mobile communication device, where the mobileapplication incorporates an event monitoring agent, in response toreceiving an input to the mobile application, executing the mobileapplication in a trusted security zone execution mode on the mobilecommunication device, and creating a genesis block of a block chain bythe mobile application executing in the trusted security zone executionmode, where the genesis block comprises information about the mobilecommunication device and about the mobile application. The methodfurther comprises creating an event block of the block chain by theevent monitoring agent executing in the trusted security zone executionmode, where the event block comprises information about at least oneprocessing event associated with executing the mobile application,attaching the event block to the block chain by the event monitoringagent executing in the trusted security zone execution mode,transmitting the block chain by the mobile application to a data store,and reverting by the mobile application to execution in the normalexecution mode.

These and other features will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, referenceis now made to the following brief description, taken in connection withthe accompanying drawings and detailed description, wherein likereference numerals represent like parts.

FIG. 1 is a block diagram of a communication system according to anembodiment of the disclosure.

FIG. 2A is a block diagram of a mobile communication device according toan embodiment of the disclosure.

FIG. 2B is a diagram of a mobile communication device according toanother embodiment of the disclosure.

FIG. 3 is a flow chart of a method according to an embodiment of thedisclosure.

FIG. 4 is a flow chart of another method according to an embodiment ofthe disclosure.

FIG. 5 is an illustration of a mobile communication device according toan embodiment of the disclosure.

FIG. 6 is a block diagram of a hardware architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 7A is a block diagram of a software architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 7B is a block diagram of another software architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 8 is a block diagram of a computer system according to anembodiment of the disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrativeimplementations of one or more embodiments are illustrated below, thedisclosed systems and methods may be implemented using any number oftechniques, whether currently known or not yet in existence. Thedisclosure should in no way be limited to the illustrativeimplementations, drawings, and techniques illustrated below, but may bemodified within the scope of the appended claims along with their fullscope of equivalents.

Mobile applications installed on a mobile communication device maydesirably capture a record of execution events and transmit this recordof execution events to a data store external to the mobile communicationdevice. Some of these execution events may comprise mobile applicationand/or mobile communication device performance metrics. It may bedesired that such records be secured and trustworthy. Said in otherwords, it may be desired that the capturing, recording, and transmissionof execution events be reasonably secured against falsification. In somecircumstances accomplishing these goals may be problematic. For example,in some circumstances an operating system that the mobile applicationsexecute on top of may not provide inherent support for such enhancedsecurity at an application execution level. The present disclosureteaches a system and methods for providing such enhanced security formobile applications.

Mobile applications may be downloaded from the Internet and installed ona mobile communication device after the device is manufactured,purchased by a user, and activated to receive wireless communicationservice. These may be referred to as user applications, user installedapplications, and/or third party applications. Because the originalequipment manufacturer (OEM) of the mobile communication device haslittle control over such third party applications (e.g., the OEM has nottested the third party application to verify its compatibility with thedevice, its freedom from defects, or its freedom from malware), oftenthe operating system support for third party applications is restrictedrelative to system applications that were installed by the OEM.

The present disclosure teaches a third party application thatincorporates instructions that cause the third party application to beexecuted in a trusted security zone (TSZ) of the mobile communicationdevice (e.g., executed in a TSZ execution mode). Trusted security zonesand associated processing are discussed further hereinafter. Theseinstructions executing in the TSZ create an initial or genesis block ofa block chain, where the genesis block comprises information about themobile communication device and the context of the execution of thethird party application, add one or more event blocks to the block chain(where each event block captures information about events occurringduring execution of the third party application), and completes theblock chain when the instructions have completed their task. A blockchain is a form of data structure where each subsequent block is linkedlogically to the preceding block. For example, each block (with theexception of the first block or genesis block) may comprise a hashcalculated over the preceding block of the block chain, a nonce value,data captured or stored by the block, and a hash of the block itselfcalculated over the hash of the preceding block, the nonce, and thedata. Typically the nonce is determined via trial and error to satisfy adesired constraint on the form of the hash of the block itself, forexample a form having a predefined number of leading zeros in the hashof the block itself. In an embodiment, a nonce is an arbitrarilydetermined integer, for example an integer generated by a pseudo-randomnumber generator.

The third party application transmits the completed block chain to adata store external to the mobile communication device, for example to adata store communicatively coupled to the Internet. The transmission ofthe completed block chain to the data store may be performed while thethird party application executes in the TSZ. Alternatively, thetransmission of the completed block chain to the data store may beperformed while the third party application executes in a normalexecution mode, after reversion from the TSZ execution mode. In thislater case, in an embodiment, the third party application may cause thecompleted block chain to be encrypted (e.g., by calling encryptionservices from the operating system of the mobile communication device orfrom a library of system support functions) and then transmits theencrypted completed block chain to the data store external to the mobilecommunication device. In an embodiment, the completed block chain firstmay be encrypted, and second the encrypted block chain may betransmitted while the third party application executes in the TSZ to thedata store. The data store may store the completed block chain inencrypted form or, alternatively, may first decrypt the completed blockchain and second store the completed block chain in decrypted form.

It is noted that such execution of the third party application orportions of the third party application in the TSZ execution mode canprovide the benefit not only of providing secure and trustworthy reports(e.g., the event block chain described above) of events occurring withinthe subject third party application but also can secure otherapplications on the mobile communication device from that subject thirdparty application. For example, when the third party applicationexecutes in the TSZ execution mode, the portions of memory that are notpart of the TSZ and where the other applications may be stored are notaccessible to the TSZ. The data store may be made accessible to avariety of stake holders who are able to present the appropriate useridentities and passwords. The stake holders may be a developer of thethird party application, a proprietor of an Internet search capabilityembedded in the third party application, a wireless communicationservice provider who provides wireless communication service to themobile communication device, and/or other authorized entities.

In an embodiment, a mobile application (e.g., a third party application)incorporates an Internet search client that, when the mobile applicationexecutes on a mobile communication device, may reach out to conduct asearch via the Internet, for example by interworking with an Internetsearch server application external to the mobile communication device.The search may be conducted based on one or more search prompts input bya user. In some circumstances it may be challenging for the mobileapplication to report this search activity back to a data store wherestake holders can analyze this search activity. This information may beused for a variety of purposes, including adapting the search serverapplication algorithms and/or rules to provide improved searchingcapability. By configuring the Internet search client to causeprocessing on the mobile communication device to execute in a TSZexecution mode, the Internet search client can both conduct an Internetsearch securely and capture a report of that search activity that can betrusted to be accurate and free from falsification.

In an embodiment, in response to receiving an input to the mobileapplication to conduct an Internet search, the mobile application causesthe mobile communication device to execute instructions of an Internetsearch client that are embedded in the mobile application in a TSZexecution mode. This may entail the mobile application requesting theoperating system to execute the mobile application or a portion of themobile application (e.g., at least some of the Internet search clientinstructions) in the TSZ execution mode. In an embodiment, the Internetsearch client instructions are executed by a graphics processor unit(GPU) of the mobile communication device in the TSZ execution mode,whereby the Internet search client can present search results in adisplay of the mobile communication device and receive user inputs tothe Internet search client as well as communicate via a radiotransceiver (e.g., a radio modem) of the mobile communication devicewith the search server application.

The Internet search client executing in the GPU creates a genesis blockthat is the start of a block chain recording the Internet search. Thegenesis block comprises information about the mobile communicationdevice, about the Internet search client, and about a search prompt. Thegenesis block may identify the mobile communication device by atelephone number, by a mobile equipment identity (MEID), or by anotheridentity. The genesis block may identify a brand or make of the mobilecommunication device and a model of the mobile communication device. Thegenesis block may identify the mobile application from within which theInternet search client is invoked. The genesis block may identify theInternet search client and a version identity of the client. The genesisblock may identify a search prompt or search string input by a user. Thegenesis block may identify the Internet search client by name. Thegenesis block may comprise an indication of the current location of themobile communication device.

The Internet search client creates one or more event blocks thatcomprise information recording events that occur during the processingof the Internet search. These event blocks may comprise informationabout results returned by the Internet search server application to theInternet search client and inputs to the Internet search client by auser of the mobile communication device (e.g., inputs provided by theuser as the search progresses). An event block may comprise searchresults. The event block may comprise information about an elapsed timebetween a search request and a search result. The event block maycomprise information about a wireless bandwidth available to the mobilecommunication device during the elapsed time, for example a number ofsub-channels allocated to the device. As each event block is created,the Internet search client attaches and/or appends it to the end of theblock chain. When the Internet search has completed, the Internet searchclient closes the block chain. The Internet search client may close theblock chain by creating a terminal block and attaching it to the end ofthe block chain. The completed block chain is then transmitted to a datastore external to the mobile communication device. In an embodiment, thecompleted block chain may be transmitted by the Internet search clientwhile it is executing on the GPU. When transmitted while the Internetsearch client is executing on the GPU in the TSZ execution mode, thecompleted block chain may be transmitted over a trusted end-to-endcommunication link to the data store. For more details on establishingtrusted end-to-end communication links relying on hardware assistedsecurity (e.g., TSZ), see U.S. Pat. No. 9,282,898, filed Jun. 25, 2012,entitled “End-to-end Trusted Communications Infrastructure,” by LeoMichael McRoberts, et al., which is hereby incorporated by reference inits entirety. Alternatively, in an embodiment, the Internet searchclient may first cause execution of the mobile application to revertfrom execution in the TSZ execution mode to the normal execution mode,and the completed block chain may second be transmitted by the Internetsearch client or by the mobile application to the data store. In thislater case, in an embodiment, the Internet search client or the mobileapplication first may cause the completed block chain to be encrypted(e.g., by calling encryption services from the operating system of themobile communication device or from a library of system supportfunctions) and second may transmit the encrypted completed block chainto the data store external to the mobile communication device. In anembodiment, the completed block chain first may be encrypted and secondthe encrypted block chain may be transmitted via a trusted end-to-endcommunication link to the data store. The data store may store thecompleted block chain in encrypted form or, alternatively, may firstdecrypt the completed block chain and then store the completed blockchain in decrypted form.

Because it was created and built in the TSZ execution mode, thecompleted block chain transmitted to and stored in the data store isdeemed to be authentic and unfalsified. The data store may provideaccess to the completed block chains that record different Internetsearches completed by a large number of different mobile communicationdevices to a proprietor of the Internet search server application, to adeveloper of the third party application embedding the Internet searchclient, and to a wireless service provider, whereby to reconcile servicelevel agreements (SLAs) and other business agreements among them.

In an embodiment, a mobile application (e.g., a media player)incorporates an event monitor that executes in a TSZ execution mode onthe mobile communication device (e.g., in a central processor unit (CPU)or in a digital signal processor (DSP) of the device), creates a genesisblock to establish a block chain, creates and appends event blocks tothe block chain, completes the block chain, and transmits the blockchain to a data store external to the mobile communication device. Theevent monitor may capture when and how often content is played by themedia player. The event monitor may capture events such as pausingplayback, rewinding playback, skipping playback of tracks, skippingadvertisements, and other events. The event monitor may create eventblocks that comprise information about a play input event, a pause inputevent, a skip input event. The event blocks may identify an item ofcontent. Some of this event information may comprise performancemetrics. The collection of this event information captured while theevent monitor executes in a TSZ execution mode may be deemed to beauthentic and unfalsified. This information can be valuable to artistswho create the content, for example for evaluating the public responseto their creations. The system and methods described herein mayadvantageously be applied to other mobile applications to capture eventsand/or performance metrics associated with execution of the mobileapplication on the mobile communication device in a secure andunfalsified manner and to store them in a data store external to themobile communication device.

A trusted security zone provides chipsets with a hardware root of trust,a secure execution environment for applications, and secure access toperipherals. A hardware root of trust means the chipset should onlyexecute programs intended by the device manufacturer or vendor andresists software and physical attacks, and therefore remains trusted toprovide the intended level of security. The chipset architecture isdesigned to promote a programmable environment that allows theconfidentiality and integrity of assets to be protected from specificattacks. Trusted security zone capabilities are becoming features inboth wireless and fixed hardware architecture designs. Providing thetrusted security zone in the main mobile communication device chipsetand protecting the hardware root of trust removes the need for separatesecure hardware to authenticate the device or user. To ensure theintegrity of the applications requiring trusted data, such as a mobilefinancial services application, the trusted security zone also providesthe secure execution environment where only trusted applications canoperate, safe from attacks. Security is further promoted by restrictingaccess of non-trusted applications to peripherals, such as data inputsand data outputs, while a trusted application is running in the secureexecution environment. In an embodiment, the trusted security zone maybe conceptualized as hardware assisted security.

A complete trusted execution environment (TEE) may be implementedthrough the use of the trusted security zone hardware and softwarearchitecture. The trusted execution environment is an executionenvironment that is parallel to the execution environment of the mainmobile communication device operating system. The trusted executionenvironment and/or the trusted security zone may provide a base layer offunctionality and/or utilities for use of applications that may executein the trusted security zone. For example, in an embodiment, trusttokens may be generated by the base layer of functionality and/orutilities of the trusted execution environment and/or trusted securityzone for use in trusted end-to-end communication links to document acontinuity of trust of the communications. For more details onestablishing trusted end-to-end communication links relying on hardwareassisted security, see U.S. Pat. No. 9,282,898, filed Jun. 25, 2012,entitled “End-to-end Trusted Communications Infrastructure,” by LeoMichael McRoberts, et al., which was incorporated by reference above.Through standardization of application programming interfaces (APIs),the trusted execution environment becomes a place to which scalabledeployment of secure services can be targeted. A device which has achipset that has a trusted execution environment on it may exist in atrusted services environment, where devices in the trusted servicesenvironment are trusted and protected against attacks. The trustedexecution environment can be implemented on mobile phones and tablets aswell as extending to other trusted devices such as personal computers,servers, sensors, medical devices, point-of-sale terminals, industrialautomation, handheld terminals, automotive, etc.

The trusted security zone is implemented by partitioning all of thehardware and software resources of the mobile communication device intotwo partitions: a secure partition and a normal partition. Placingsensitive resources in the secure partition can protect against possibleattacks on those resources. For example, resources such as trustedsoftware applications may run in the secure partition and have access tohardware peripherals such as a touchscreen or a secure location inmemory. Less secure peripherals such as wireless radios may be disabledcompletely while the secure partition is being accessed, while otherperipherals may only be accessed from the secure partition. While thesecure partition is being accessed through the trusted executionenvironment, the main mobile operating system in the normal partition issuspended, and applications in the normal partition are prevented fromaccessing the secure peripherals and data. This prevents corruptedapplications or malware applications from breaking the trust of thedevice.

The trusted security zone is implemented by partitioning the hardwareand software resources to exist in a secure subsystem which is notaccessible to components outside the secure subsystem. The trustedsecurity zone is built into the processor architecture at the time ofmanufacture through hardware logic present in the trusted security zonewhich enables a perimeter boundary between the secure partition and thenormal partition. The trusted security zone may only be manipulated bythose with the proper credential and, in an embodiment, may not be addedto the chip after it is manufactured. Software architecture to supportthe secure partition may be provided through a dedicated secure kernelrunning trusted applications. Trusted applications are independentsecure applications which can be accessed by normal applications throughan application programming interface in the trusted executionenvironment on a chipset that utilizes the trusted security zone.

In an embodiment, the normal partition applications run on a firstvirtual processor, and the secure partition applications run on a secondvirtual processor. Both virtual processors may run on a single physicalprocessor, executing in a time-sliced fashion, removing the need for adedicated physical security processor. Time-sliced execution comprisesswitching contexts between the two virtual processors to share processorresources based on tightly controlled mechanisms such as secure softwareinstructions or hardware exceptions. The context of the currentlyrunning virtual processor is saved, the context of the virtual processorbeing switched to is restored, and processing is restarted in therestored virtual processor. Time-sliced execution protects the trustedsecurity zone by stopping the execution of the normal partition whilethe secure partition is executing.

The two virtual processors context switch via a processor mode calledmonitor mode when changing the currently running virtual processor. Themechanisms by which the processor can enter monitor mode from the normalpartition are tightly controlled. The entry to monitor mode can betriggered by software executing a dedicated instruction, the SecureMonitor Call (SMC) instruction, or by a subset of the hardware exceptionmechanisms such as hardware interrupts, which can be configured to causethe processor to switch into monitor mode. The software that executeswithin monitor mode then saves the context of the running virtualprocessor and switches to the secure virtual processor.

The trusted security zone runs a separate operating system that is notaccessible to the device users. For security purposes, the trustedsecurity zone is not open to users for installing applications, whichmeans users do not have access to install applications in the trustedsecurity zone. This prevents corrupted applications or malwareapplications from executing powerful instructions reserved to thetrusted security zone and thus preserves the trust of the device. Thesecurity of the system is achieved at least in part by partitioning thehardware and software resources of the mobile phone so they exist in oneof two partitions, the secure partition for the security subsystem andthe normal partition for everything else. Placing the trusted securityzone in the secure partition and restricting access from the normalpartition protects against software and basic hardware attacks. Hardwarelogic ensures that no secure partition resources can be accessed by thenormal partition components or applications. A dedicated securepartition operating system runs in a virtual processor separate from thenormal partition operating system that likewise executes in its ownvirtual processor. Users may install applications on the mobilecommunication device which may execute in the normal partition operatingsystem described above. The trusted security zone runs a separateoperating system for the secure partition that is installed by themobile communication device manufacturer or vendor, and users are notable to install new applications in or alter the contents of the trustedsecurity zone.

Turning now to FIG. 1, a system 100 is described. In an embodiment,system 100 comprises a mobile communication device (user equipment—UE)102 that comprises a radio transceiver 104, a central processing unit(CPU) 106, a graphics processor unit (GPU) 108, a memory 110, and adisplay 112. The UE 102 may be one of a mobile phone, a smart phone, apersonal digital assistant (PDA), a wearable computer, a headsetcomputer, a laptop computer, a notebook computer, or a tablet computer.The UE 102 may establish a radio communication link to a cell site 116according to one or more of a long term evolution (LTE), a code divisionmultiple access (CDMA), a global system for mobile communications (GSM),or a worldwide interoperability for microwave access (WiMAX)telecommunication protocol. The UE 102 may establish a radiocommunication link to the cell site 116 using a 5G telecommunicationprotocol. The cell site 116 provides connectivity of the UE 102 to anetwork 118. In an embodiment, the UE 102 further comprises a WiFi radiotransceiver that may establish a wireless link to a WiFi access point(not shown), and the WiFi access point may communicatively couple the UE102 to the network 118. The network 118 comprises one or more privatenetworks, one or more public networks, or a combination thereof. Thesystem 100 comprises any number of UEs 102 and any number of cell sites116.

The memory 110 comprises a non-transitory portion that stores one ormore mobile applications 124. In an embodiment, the mobile application124 may encapsulate an Internet search client that communicates with aserver 120 via the cell site 116 and via the network 118 to completeInternet searches. The Internet search client may build a block chainthat records information pertinent to the Internet searching activityand transmit this block chain to a data store 125. One or more metricsconsumers 126 may access the data store 125 to read the block chainsstored there by UEs 102. The metrics consumers may be developers of themobile application 124, a proprietor of the Internet search serverapplication 122, a wireless service provider that provides radiocommunication service to the UE 102, and others. The system 100comprises any number of servers 120 and any number of data stores 124.In an embodiment, the mobile application 124 may encapsulate an eventmonitor that build a block chain that records events occurring duringthe processing of the mobile application 124 and transmit this blockchain to the data store 125.

Turning now to FIG. 2A, details of an embodiment of the UE 102 aredescribed. In an embodiment, the mobile application 124 comprises anInternet search client 134. The UE 102 is configured to be able toexecute instructions in both a normal execution mode 130 and in atrusted security zone (TSZ) execution mode 132. The CPU 106 and the GPU108 are both configured to be capable of executing instructions ineither the normal execution mode 130 or the TSZ execution mode 132. Inan embodiment, the memory 110 may comprise a portion associated with thenormal execution mode 130 and a portion associated with the TSZexecution mode 132. When the search client 134 (or a selection ofinstructions of the search client 134) is executed in the TSZ executionmode 132, the search client 134 may build a block chain comprising agenesis block 136, a plurality of event blocks 138, and a terminal block140.

The mobile application 124 may be a mobile video game. The mobileapplication 124 may be an investment application. The mobile application124 may be a special interest application, such as a wine amateurapplication, a bird watcher application, an amateur astronomyapplication, an amateur photographer application. Any of these differentspecial interest applications may embedded an Internet search client toenable the user to conduct Internet searches from within the amateurinterest application.

Turning now to FIG. 2B, details of another embodiment of the UE 102 aredescribed. In an embodiment, the mobile application 124 comprises anevent monitor 150. When the mobile application 124 executes, at least aportion of the event monitor 150 executes in the TSZ execution mode 132.For example, the mobile application 124 may execute instructions, andthe event monitor 150 executing in the normal execution mode 130 keepstrack of what the mobile application 124 does and keeps track of processvalues and/or user inputs. When the mobile application 124 has completedexecution and is preparing to shut down, the event monitor 150 requeststo execute in the TSZ execution mode 132. The event monitor 150 maybuild a block chain comprising a genesis block 136, a plurality of eventblocks 138, and a terminal block 140. The event blocks 138 may store theevents that occurred during execution of the mobile application 124 andthe process values and/or user inputs. The event monitor 150 maytransmit the block chain to the data store 125 while it is executing inthe TSZ execution mode 132, and then the event monitor 150 may revert tothe normal execution mode 130. Alternatively, the event monitor 150 mayrevert to the normal execution mode 130, and then transmit the blockchain to the data store 125 while it is executing in the normalexecution mode 130. In an embodiment, the mobile application may be amedia player, and the event monitor 150 may monitor and capture mediaplayback events and/or user input events.

Turning now to FIG. 3, a method 200 is described. In an embodiment, themethod 200 is a method of performing an Internet search from within amobile application. At block 202, the method 200 comprises executing amobile application in a normal execution mode on a mobile communicationdevice, where the mobile application incorporates an Internet searchclient. The mobile application may be a gaming application. The mobileapplication may be a special interest application. The mobileapplication may be a restaurant finding application. At block 204, themethod 200 comprises, in response to receiving an input to the mobileapplication selecting the Internet search client, executing the mobileapplication in a trusted security zone (TSZ) execution mode on themobile communication device wherein the mobile application executesinstructions of the Internet search client in a graphics processing unit(GPU) of the mobile communication device. In another embodiment, themobile application executes instructions of the Internet search clientin a central processing unit (CPU) of the mobile communication device,in a digital signal processor (DSP) of the mobile communication device,in a field programmable gate array (FPGA) of the mobile communicationdevice, or in an application integrated circuit (ASIC) of the mobilecommunication device.

At block 206, the method 200 comprises creating a genesis block of ablock chain by the Internet search client instructions executing in theGPU, where the genesis block comprises information about the mobilecommunication device and about a search prompt. In an embodiment, thegenesis block may comprise additional information such as one or more ofan identity of the Internet search client, a version identity of theInternet search client, a location of the mobile communication device,or an identity of a cell site from which the mobile communication devicereceives a wireless communication link. At block 208, the method 200comprises creating an event block of the block chain by the Internetsearch client instructions executing in the GPU, where the event blockcomprises information about at least one processing event associatedwith executing an Internet search. The processing event may comprise auser input of a search prompt or a search string. The processing eventmay comprise a result of an Internet search. The processing event maycomprise a search error message.

At block 210, the method 200 comprises attaching the event block to theblock chain by the Internet search client instructions executing in theGPU. At block 212, the method 200 comprises closing the block chain bythe Internet search client instructions executing in the GPU. In anembodiment, the processing of block 212 does not occur and the blockchain is closed simply by not adding additional event blocks to theblock chain.

At block 214, the method 200 comprises transmitting the block chain bythe mobile communication device to a data store. In an embodiment, theprocessing of block 214 happens while the Internet search clientinstructions are executing in the GPU. In an embodiment, the processingof block 214 happens while the Internet search client instructions areexecuting in the TSZ execution mode in the GPU. At block 216, the method200 comprises reverting by the mobile application to execution in thenormal execution mode. In an embodiment, the processing of block 214happens after the mobile application reverts to execution in the normalexecution mode.

Turning now to FIG. 4, a method 220 is described. In an embodiment,method 200 is a method of executing a mobile application. At block 222,the method 220 comprises executing a mobile application in a normalexecution mode on a mobile communication device, where the mobileapplication incorporates an event monitoring agent. At block 224, themethod 220 comprises, in response to receiving an input to the mobileapplication, executing the mobile application in a trusted security zoneexecution mode on the mobile communication device.

At block 226, the method 220 comprises creating a genesis block of ablock chain by the mobile application executing in the trusted securityzone (TSZ) execution mode, where the genesis block comprises informationabout the mobile communication device and about the mobile application.At block 228, the method 220 comprises creating an event block of theblock chain by the event monitoring agent executing in the trustedsecurity zone execution mode, where the event block comprisesinformation about at least one processing event associated withexecuting the mobile application.

At block 230, the method 220 comprises attaching the event block to theblock chain by the event monitoring agent executing in the trustedsecurity zone execution mode. At block 232, the method 220 comprisesclosing the block chain by the event monitoring agent executing in thetrusted security zone execution mode. In an embodiment, the processingof block 232 does not occur and the block chain is closed simply by notadding additional event blocks to the block chain.

At block 234, the method 220 comprises transmitting the block chain bythe mobile application to a data store. At block 236, the method 220comprises reverting by the mobile application to execution in the normalexecution mode.

FIG. 5 depicts the user equipment (UE) 400, which is operable forimplementing aspects of the present disclosure, but the presentdisclosure should not be limited to these implementations. Thoughillustrated as a mobile phone, the UE 400 may take various formsincluding a wireless handset, a pager, a personal digital assistant(PDA), a gaming device, or a media player. The UE 400 includes atouchscreen display 402 having a touch-sensitive surface for input by auser. A small number of application icons 404 are illustrated within thetouch screen display 402. It is understood that in differentembodiments, any number of application icons 404 may be presented in thetouch screen display 402. In some embodiments of the UE 400, a user maybe able to download and install additional applications on the UE 400,and an icon associated with such downloaded and installed applicationsmay be added to the touch screen display 402 or to an alternativescreen. The UE 400 may have other components such as electro-mechanicalswitches, speakers, camera lenses, microphones, input and/or outputconnectors, and other components as are well known in the art. The UE400 may present options for the user to select, controls for the user toactuate, and/or cursors or other indicators for the user to direct. TheUE 400 may further accept data entry from the user, including numbers todial or various parameter values for configuring the operation of thehandset. The UE 400 may further execute one or more software or firmwareapplications in response to user commands. These applications mayconfigure the UE 400 to perform various customized functions in responseto user interaction. Additionally, the UE 400 may be programmed and/orconfigured over-the-air, for example from a wireless base station, awireless access point, or a peer UE 400. The UE 400 may execute a webbrowser application which enables the touch screen display 402 to show aweb page. The web page may be obtained via wireless communications witha base transceiver station, a wireless network access node, a peer UE400 or any other wireless communication network or system.

FIG. 6 shows a block diagram of the UE 400. While a variety of knowncomponents of handsets are depicted, in an embodiment a subset of thelisted components and/or additional components not listed may beincluded in the UE 400. The UE 400 includes a digital signal processor(DSP) 502 and a memory 504. As shown, the UE 400 may further include anantenna and front end unit 506, a radio frequency (RF) transceiver 508,a baseband processing unit 510, a microphone 512, an earpiece speaker514, a headset port 516, an input/output interface 518, a removablememory card 520, a universal serial bus (USB) port 522, an infrared port524, a vibrator 526, one or more electro-mechanical switches 528, atouch screen liquid crystal display (LCD) with a touch screen display530, a touch screen/LCD controller 532, a camera 534, a cameracontroller 536, and a global positioning system (GPS) receiver 538. Inan embodiment, the UE 400 may include another kind of display that doesnot provide a touch sensitive screen. In an embodiment, the UE 400 mayinclude both the touch screen display 530 and additional displaycomponent that does not provide a touch sensitive screen. In anembodiment, the DSP 502 may communicate directly with the memory 504without passing through the input/output interface 518. Additionally, inan embodiment, the UE 400 may comprise other peripheral devices thatprovide other functionality.

The DSP 502 or some other form of controller or central processing unitoperates to control the various components of the UE 400 in accordancewith embedded software or firmware stored in memory 504 or stored inmemory contained within the DSP 502 itself. In addition to the embeddedsoftware or firmware, the DSP 502 may execute other applications storedin the memory 504 or made available via information carrier media suchas portable data storage media like the removable memory card 520 or viawired or wireless network communications. The application software maycomprise a compiled set of machine-readable instructions that configurethe DSP 502 to provide the desired functionality, or the applicationsoftware may be high-level software instructions to be processed by aninterpreter or compiler to indirectly configure the DSP 502.

The DSP 502 may communicate with a wireless network via the analogbaseband processing unit 510. In some embodiments, the communication mayprovide Internet connectivity, enabling a user to gain access to contenton the Internet and to send and receive e-mail or text messages. Theinput/output interface 518 interconnects the DSP 502 and variousmemories and interfaces. The memory 504 and the removable memory card520 may provide software and data to configure the operation of the DSP502. Among the interfaces may be the USB port 522 and the infrared port524. The USB port 522 may enable the UE 400 to function as a peripheraldevice to exchange information with a personal computer or othercomputer system. The infrared port 524 and other optional ports such asa Bluetooth® interface or an IEEE 802.11 compliant wireless interfacemay enable the UE 400 to communicate wirelessly with other nearbyhandsets and/or wireless base stations. In an embodiment, the UE 400 maycomprise a near field communication (NFC) transceiver. The NFCtransceiver may be used to complete payment transactions withpoint-of-sale terminals or other communications exchanges. In anembodiment, the UE 400 may comprise a radio frequency identify (RFID)reader and/or writer device.

The switches 528 may couple to the DSP 502 via the input/outputinterface 518 to provide one mechanism for the user to provide input tothe UE 400. Alternatively, one or more of the switches 528 may becoupled to a motherboard of the UE 400 and/or to components of the UE400 via a different path (e.g., not via the input/output interface 518),for example coupled to a power control circuit (power button) of the UE400. The touch screen display 530 is another input mechanism, whichfurther displays text and/or graphics to the user. The touch screen LCDcontroller 532 couples the DSP 502 to the touch screen display 530. TheGPS receiver 538 is coupled to the DSP 502 to decode global positioningsystem signals, thereby enabling the UE 400 to determine its position.

FIG. 7A illustrates a software environment 602 that may be implementedby the DSP 502. The DSP 502 executes operating system software 604 thatprovides a platform from which the rest of the software operates. Theoperating system software 604 may provide a variety of drivers for thehandset hardware with standardized interfaces that are accessible toapplication software. The operating system software 604 may be coupledto and interact with application management services (AMS) 606 thattransfer control between applications running on the UE 400. Also shownin FIG. 7A are a web browser application 608, a media player application610, and JAVA applets 612. The web browser application 608 may beexecuted by the UE 400 to browse content and/or the Internet, forexample when the UE 400 is coupled to a network via a wireless link. Theweb browser application 608 may permit a user to enter information intoforms and select links to retrieve and view web pages. The media playerapplication 610 may be executed by the UE 400 to play audio oraudiovisual media. The JAVA applets 612 may be executed by the UE 400 toprovide a variety of functionality including games, utilities, and otherfunctionality.

FIG. 7B illustrates an alternative software environment 620 that may beimplemented by the DSP 502. The DSP 502 executes operating system kernel(OS kernel) 628 and an execution runtime 630. The DSP 502 executesapplications 622 that may execute in the execution runtime 630 and mayrely upon services provided by the application framework 624.Applications 622 and the application framework 624 may rely uponfunctionality provided via the libraries 626.

FIG. 8 illustrates a computer system 380 suitable for implementing oneor more embodiments disclosed herein. The computer system 380 includes aprocessor 382 (which may be referred to as a central processor unit orCPU) that is in communication with memory devices including secondarystorage 384, read only memory (ROM) 386, random access memory (RAM) 388,input/output (I/O) devices 390, and network connectivity devices 392.The processor 382 may be implemented as one or more CPU chips.

It is understood that by programming and/or loading executableinstructions onto the computer system 380, at least one of the CPU 382,the RAM 388, and the ROM 386 are changed, transforming the computersystem 380 in part into a particular machine or apparatus having thenovel functionality taught by the present disclosure. It is fundamentalto the electrical engineering and software engineering arts thatfunctionality that can be implemented by loading executable softwareinto a computer can be converted to a hardware implementation bywell-known design rules. Decisions between implementing a concept insoftware versus hardware typically hinge on considerations of stabilityof the design and numbers of units to be produced rather than any issuesinvolved in translating from the software domain to the hardware domain.Generally, a design that is still subject to frequent change may bepreferred to be implemented in software, because re-spinning a hardwareimplementation is more expensive than re-spinning a software design.Generally, a design that is stable that will be produced in large volumemay be preferred to be implemented in hardware, for example in anapplication specific integrated circuit (ASIC), because for largeproduction runs the hardware implementation may be less expensive thanthe software implementation. Often a design may be developed and testedin a software form and later transformed, by well-known design rules, toan equivalent hardware implementation in an application specificintegrated circuit that hardwires the instructions of the software. Inthe same manner as a machine controlled by a new ASIC is a particularmachine or apparatus, likewise a computer that has been programmedand/or loaded with executable instructions may be viewed as a particularmachine or apparatus.

Additionally, after the system 380 is turned on or booted, the CPU 382may execute a computer program or application. For example, the CPU 382may execute software or firmware stored in the ROM 386 or stored in theRAM 388. In some cases, on boot and/or when the application isinitiated, the CPU 382 may copy the application or portions of theapplication from the secondary storage 384 to the RAM 388 or to memoryspace within the CPU 382 itself, and the CPU 382 may then executeinstructions that the application is comprised of. In some cases, theCPU 382 may copy the application or portions of the application frommemory accessed via the network connectivity devices 392 or via the I/Odevices 390 to the RAM 388 or to memory space within the CPU 382, andthe CPU 382 may then execute instructions that the application iscomprised of. During execution, an application may load instructionsinto the CPU 382, for example load some of the instructions of theapplication into a cache of the CPU 382. In some contexts, anapplication that is executed may be said to configure the CPU 382 to dosomething, e.g., to configure the CPU 382 to perform the function orfunctions promoted by the subject application. When the CPU 382 isconfigured in this way by the application, the CPU 382 becomes aspecific purpose computer or a specific purpose machine.

The secondary storage 384 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 388 is not large enough tohold all working data. Secondary storage 384 may be used to storeprograms which are loaded into RAM 388 when such programs are selectedfor execution. The ROM 386 is used to store instructions and perhapsdata which are read during program execution. ROM 386 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage 384. The RAM 388 is usedto store volatile data and perhaps to store instructions. Access to bothROM 386 and RAM 388 is typically faster than to secondary storage 384.The secondary storage 384, the RAM 388, and/or the ROM 386 may bereferred to in some contexts as computer readable storage media and/ornon-transitory computer readable media.

I/O devices 390 may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices.

The network connectivity devices 392 may take the form of modems, modembanks, Ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards that promote radio communications using protocols suchas code division multiple access (CDMA), global system for mobilecommunications (GSM), long-term evolution (LTE), worldwideinteroperability for microwave access (WiMAX), near field communications(NFC), radio frequency identity (RFID), and/or other air interfaceprotocol radio transceiver cards, and other well-known network devices.These network connectivity devices 392 may enable the processor 382 tocommunicate with the Internet or one or more intranets. With such anetwork connection, it is contemplated that the processor 382 mightreceive information from the network, or might output information to thenetwork in the course of performing the above-described method steps.Such information, which is often represented as a sequence ofinstructions to be executed using processor 382, may be received fromand outputted to the network, for example, in the form of a computerdata signal embodied in a carrier wave.

Such information, which may include data or instructions to be executedusing processor 382 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembedded in the carrier wave, or other types of signals currently usedor hereafter developed, may be generated according to several methodswell-known to one skilled in the art. The baseband signal and/or signalembedded in the carrier wave may be referred to in some contexts as atransitory signal.

The processor 382 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 384), flash drive, ROM 386, RAM 388, or the network connectivitydevices 392. While only one processor 382 is shown, multiple processorsmay be present. Thus, while instructions may be discussed as executed bya processor, the instructions may be executed simultaneously, serially,or otherwise executed by one or multiple processors. Instructions,codes, computer programs, scripts, and/or data that may be accessed fromthe secondary storage 384, for example, hard drives, floppy disks,optical disks, and/or other device, the ROM 386, and/or the RAM 388 maybe referred to in some contexts as non-transitory instructions and/ornon-transitory information.

In an embodiment, the computer system 380 may comprise two or morecomputers in communication with each other that collaborate to perform atask. For example, but not by way of limitation, an application may bepartitioned in such a way as to permit concurrent and/or parallelprocessing of the instructions of the application. Alternatively, thedata processed by the application may be partitioned in such a way as topermit concurrent and/or parallel processing of different portions of adata set by the two or more computers. In an embodiment, virtualizationsoftware may be employed by the computer system 380 to provide thefunctionality of a number of servers that is not directly bound to thenumber of computers in the computer system 380. For example,virtualization software may provide twenty virtual servers on fourphysical computers. In an embodiment, the functionality disclosed abovemay be provided by executing the application and/or applications in acloud computing environment. Cloud computing may comprise providingcomputing services via a network connection using dynamically scalablecomputing resources. Cloud computing may be supported, at least in part,by virtualization software. A cloud computing environment may beestablished by an enterprise and/or may be hired on an as-needed basisfrom a third party provider. Some cloud computing environments maycomprise cloud computing resources owned and operated by the enterpriseas well as cloud computing resources hired and/or leased from a thirdparty provider.

In an embodiment, some or all of the functionality disclosed above maybe provided as a computer program product. The computer program productmay comprise one or more computer readable storage medium havingcomputer usable program code embodied therein to implement thefunctionality disclosed above. The computer program product may comprisedata structures, executable instructions, and other computer usableprogram code. The computer program product may be embodied in removablecomputer storage media and/or non-removable computer storage media. Theremovable computer readable storage medium may comprise, withoutlimitation, a paper tape, a magnetic tape, magnetic disk, an opticaldisk, a solid state memory chip, for example analog magnetic tape,compact disk read only memory (CD-ROM) disks, floppy disks, jump drives,digital cards, multimedia cards, and others. The computer programproduct may be suitable for loading, by the computer system 380, atleast portions of the contents of the computer program product to thesecondary storage 384, to the ROM 386, to the RAM 388, and/or to othernon-volatile memory and volatile memory of the computer system 380. Theprocessor 382 may process the executable instructions and/or datastructures in part by directly accessing the computer program product,for example by reading from a CD-ROM disk inserted into a disk driveperipheral of the computer system 380. Alternatively, the processor 382may process the executable instructions and/or data structures byremotely accessing the computer program product, for example bydownloading the executable instructions and/or data structures from aremote server through the network connectivity devices 392. The computerprogram product may comprise instructions that promote the loadingand/or copying of data, data structures, files, and/or executableinstructions to the secondary storage 384, to the ROM 386, to the RAM388, and/or to other non-volatile memory and volatile memory of thecomputer system 380.

In some contexts, the secondary storage 384, the ROM 386, and the RAM388 may be referred to as a non-transitory computer readable medium or acomputer readable storage media. A dynamic RAM embodiment of the RAM388, likewise, may be referred to as a non-transitory computer readablemedium in that while the dynamic RAM receives electrical power and isoperated in accordance with its design, for example during a period oftime during which the computer system 380 is turned on and operational,the dynamic RAM stores information that is written to it. Similarly, theprocessor 382 may comprise an internal RAM, an internal ROM, a cachememory, and/or other internal non-transitory storage blocks, sections,or components that may be referred to in some contexts as non-transitorycomputer readable media or computer readable storage media.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted or not implemented.

Also, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as directly coupled or communicating witheach other may be indirectly coupled or communicating through someinterface, device, or intermediate component, whether electrically,mechanically, or otherwise. Other examples of changes, substitutions,and alterations are ascertainable by one skilled in the art and could bemade without departing from the spirit and scope disclosed herein.

What is claimed is:
 1. A method of performing an Internet search fromwithin a mobile application, comprising: executing a mobile applicationin a normal execution mode on a mobile communication device, where themobile application incorporates an Internet search client; in responseto receiving an input to the mobile application selecting the Internetsearch client, executing the mobile application in a trusted securityzone execution mode on the mobile communication device, wherein themobile application executes instructions of the Internet search clientin a graphics processing unit (GPU) of the mobile communication device;while executing the mobile application in the trusted security zoneexecution mode on the mobile communication device: creating a genesisblock of a block chain by the Internet search client instructionsexecuting in the GPU, where the genesis block comprises informationabout the mobile communication device and about a search prompt;creating an event block of the block chain by the Internet search clientinstructions executing in the GPU, where the event block comprisesinformation about at least one processing event associated withexecuting an Internet search; attaching the event block to the blockchain by the Internet search client instructions executing in the GPU;closing the block chain by the Internet search client instructionsexecuting in the GPU; and transmitting the block chain by the mobilecommunication device to a data store; and reverting by the mobileapplication to execution of the mobile application in the normalexecution mode.
 2. The method of claim 1, wherein each event blockcomprises a hash value of a preceding block of the block chain, a nonce,and a hash calculated over the event block itself.
 3. The method ofclaim 1, wherein the genesis block comprises a location of the mobilecommunication device.
 4. The method of claim 1, wherein the genesisblock comprises an identity of the Internet search client.
 5. The methodof claim 1, wherein the at least one processing event comprises a searchresult.
 6. The method of claim 1, wherein the at least one processingevent comprises a search prompt.
 7. The method of claim 1, wherein themobile communication device is one of a mobile phone, a smart phone, awearable computer, a personal digital assistant (PDA), a headsetcomputer, a laptop computer, a notebook computer, and a tablet computer.8. The method of claim 1, further comprising: executing a second mobileapplication in a normal execution mode on the mobile communicationdevice, where the second mobile application incorporates an eventmonitoring agent; in response to receiving an input to the second mobileapplication, executing the second mobile application in a trustedsecurity zone execution mode on the mobile communication device;creating a genesis block of a second block chain by the second mobileapplication executing in the trusted security zone execution mode, wherethe genesis block of the second block chain comprises information aboutthe mobile communication device and about the second mobile application;creating an event block of the second block chain by the eventmonitoring agent executing in the trusted security zone execution mode,where the event block of the second block chain comprises informationabout at least one processing event associated with executing the secondmobile application; attaching the event block to the second block chainby the event monitoring agent executing in the trusted security zoneexecution mode; transmitting the second block chain by the second mobileapplication to a second data store; and reverting by the second mobileapplication to execution in the normal execution mode.
 9. The method ofclaim 8, wherein the second mobile application is a media player. 10.The method of claim 8, wherein the event block of the second block chaincomprises information about at least one event selected from the listconsisting of a play input event, a pause input event, and a skip inputevent.
 11. The method of claim 10, wherein the event block of the secondblock chain comprises information that identifies an item of content.12. The method of claim 8, wherein the second mobile applicationtransmits the second block chain while executing in the trusted securityzone execution mode.
 13. The method of claim 8, wherein the secondmobile application transmits the second block chain while executing inthe normal execution mode.
 14. A mobile communication device,comprising: a central processing unit (CPU); a graphics processing unit(GPU); a non-transitory memory comprising a mobile applicationincorporating an Internet search client that, when the mobileapplication is executed by at least one of the CPU and the GPU: executesthe mobile application in a normal execution mode on the mobilecommunication device, receives an input selecting the Internet searchclient, in response to the input, begins execution of the mobileapplication in a trusted security zone execution mode, whereininstructions of the Internet search client execute in the GPU, duringexecution of the mobile application in the trusted security zoneexecution mode: creates a genesis block of a block chain via theInternet search client instructions executing in the GPU, where thegenesis block comprises information about the mobile communicationdevice and about a search prompt, creates an event block of the blockchain via the Internet search client instructions executing in the GPU,where the event block comprises information about at least oneprocessing event associated with executing an Internet search, attachesthe event block to the block chain via the Internet search clientinstructions executing in the GPU, and transmits the block chain to adata store, and reverts to execution in the normal execution mode. 15.The mobile communication device of claim 14, wherein the mobilecommunication device comprises a radio transceiver that is configured toestablish a wireless communication link according to at least one of along term evolution (LTE), a code division multiple access (CDMA), aglobal system for mobile communications (GSM), or a worldwideinteroperability for microwave access (WiMAX) telecommunicationprotocol.
 16. The mobile communication device of claim 14, wherein theevent block comprises information about an elapsed time between a searchrequest and a search result.
 17. The mobile communication device ofclaim 16, wherein the event block that comprises information about theelapsed time further comprises information about a wireless bandwidthavailable to the mobile communication device during the elapsed time.18. The mobile communication device of claim 14, wherein the genesisblock comprises information identifying a phone number of the mobilecommunication device, identifying a brand of the mobile communicationdevice, and identifying a model of the mobile communication device. 19.The mobile communication device of claim 14, wherein the genesis blockcomprises information identifying the mobile application.
 20. The mobilecommunication device of claim 14, further comprising closing the blockchain by the Internet search client instructions executing in the GPU.